Activity Continuation Between Electronic Devices

ABSTRACT

The described embodiments transfer an activity from a source electronic device to a companion electronic device. The source electronic device receives activity information describing an activity performed in a first application at the source electronic device, determines an activity identifier for the activity information, and broadcasts an activity advertisement comprising the activity identifier. Upon receiving the activity advertisement, the companion electronic device determines whether a second application that is associated with the first application is available at the companion electronic device. If the second application is available, the companion electronic device requests extended activity data from the source electronic device. The source electronic device responds by sending extended activity data from the first application to the companion electronic device. Then, the companion electronic device uses the extended activity data to configure the second application and commences performing the activity with the second application at the companion electronic device.

INCORPORATION BY REFERENCE: DISCLAIMER

Each of the following applications are hereby incorporated by reference:application Ser. No. 14/586,566, filed on 30 Dec. 2014; application No.62/005,781, filed on 30 May 2014. The instant application is related toU.S. patent application Ser. No. 14/586,511, now U.S. Pat. No.9,544,714, which is titled “Companion Application for ActivityCooperation,” filed on 30 Dec. 2014, the same day as the instantapplication. The Applicant hereby rescinds any disclaimer of claim scopein the parent application(s) or the prosecution history thereof andadvises the USPTO that the claims in this application may be broaderthan any claim in the parent application(s).

The instant application is also related to U.S. patent application Ser.No. 14/475,329, now U.S. Pat. No. 9,549,375, which is titled “OperatingMode Transitions based on Advertising Information,” filed on 2 Sep.2014, the contents of which are incorporated herein by reference.

The instant application is also related to U.S. patent application Ser.No. 14/474,466, now U.S. Pat. No. 9,451,438 which is titled “PredefinedWireless Pairing,” filed on 2 Sep. 2014, the contents of which areincorporated herein by reference.

BACKGROUND Field

The disclosed embodiments relate to electronic devices. Morespecifically, the disclosed embodiments relate to activity continuationbetween electronic devices.

Related Art

Recent advances in computer technology have enabled manufacturers toproduce powerful computing devices in various form factors, therebyenabling users to use a device as small and portable as a smartphone ora tablet to perform tasks that once required a desktop or laptopcomputer. Because of these advances, users often possess and usemultiple computing devices, e.g., a smartphone while on the road, atablet in meetings, and a laptop or desktop computer at a desk.

Although a user may possess different devices, each with powerfulcomputing capabilities, in certain cases, the user may find him- orherself using a device that is ill-suited for a task being performed orfor the situation that the user is in. For example, the user may startwhat is intended as a short email on a device such as a smartphone witha small display screen and then, due to the size of the display screen,may have a difficult time entering and editing text in the email whenthe email turns out to be longer than anticipated. Alternatively, theuser may be reading a web page or watching a movie on a desktop but mayhave to leave the room in which the desktop is located. Although theuser may retrieve another device and start the task, this is cumbersome.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 presents a block diagram illustrating an electronic device inaccordance with some embodiments.

FIG. 2 presents a block diagram illustrating a network environment inaccordance with some embodiments.

FIG. 3 presents a flowchart illustrating a process for broadcasting anactivity advertisement message in accordance with some embodiments.

FIG. 4 presents a flowchart illustrating a process for storing activityinformation describing activities that are available at a companionelectronic device in accordance with some embodiments.

FIG. 5 presents a flowchart illustrating a process for requestingextended activity data and transferring an activity in accordance withsome embodiments.

FIG. 6 presents a flowchart illustrating a process for responding to arequest for extended activity data in accordance with some embodiments.

FIG. 7 presents a flowchart illustrating a process for determiningwhether the second application is available at a companion electronicdevice in accordance with some embodiments.

FIG. 8 presents a flowchart illustrating a process for determining thesecond application using a flag in accordance with some embodiments.

FIG. 9 presents a flowchart illustrating a process for determiningwhether the second application is available when the activity identifieridentifies an entry in a structure that stores advertised activities inaccordance with some embodiments.

FIG. 10 presents a flowchart illustrating a process for determining amost recent activity from two or more activity advertisement messages inaccordance with some embodiments.

FIG. 11 presents a block diagram illustrating activity information inaccordance with some embodiments.

FIG. 12 presents a block diagram illustrating an advertised-activitytable in accordance with some embodiments.

FIG. 13 presents a block diagram illustrating an activity advertisementmessage in accordance with some embodiments.

FIG. 14 presents a block diagram illustrating a resumable-activityindication in accordance with some embodiments.

FIG. 15 presents a swim lane diagram illustrating messages exchangedbetween electronic devices in accordance with some embodiments.

FIG. 16 presents a block diagram illustrating electronic devices inproximity to one another in accordance with some embodiments.

In the figures, like reference numerals refer to the same figureelements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the described embodiments, and is provided inthe context of a particular application and its requirements. Variousmodifications to the described embodiments will be readily apparent tothose skilled in the art, and the general principles defined herein maybe applied to other embodiments and applications without departing fromthe spirit and scope of the described embodiments. Thus, the describedembodiments are not limited to the embodiments shown, but are to beaccorded the widest scope consistent with the principles and featuresdisclosed herein.

In some embodiments, an electronic device (e.g., electronic device 100in FIG. 1 and/or some portion thereof) uses code and/or data stored on acomputer-readable storage medium to perform some or all of theoperations herein described. More specifically,the electronic devicereads the code and/or data from the computer-readable storage medium andexecutes the code and/or uses the data when performing the describedoperations. In these embodiments, a computer-readable storage medium canbe any device or medium or combination thereof that stores code and/ordata for use by an electronic device. For example, the computer-readablestorage medium can include, but is not limited to, volatile memory ornon-volatile memory, such as semiconductor memories (e.g., flash memory,random access memory (eDRAM, RAM, SRAM, DRAM, DDR, DDR2/DDR3/DDR4 SDRAM,etc.), etc.) and/or magnetic or optical storage mediums (e.g., diskdrives, magnetic tape, CDs, DVDs). In the described embodiments, thecomputer-readable storage medium does not include non-statutorycomputer-readable storage mediums such as transitory signals.

In some embodiments, one or more hardware modules are configured toperform the operations herein described. For example, the hardwaremodules can comprise, but are not limited to, one or moreprocessors/cores/central processing units (CPUs), application-specificintegrated circuit (ASIC) chips, field-programmable gate arrays (FPGAs),caches/cache controllers, memory management units, compute units,embedded processors, graphics processors (GPUs)/graphics cores,pipelines, and/or other programmable-logic devices. When such hardwaremodules are activated, the hardware modules perform some or all of theoperations. In some embodiments, the hardware modules include one ormore general-purpose circuits that are configured by executinginstructions (program code, firmware, etc.) to perform the operations.

In this description, functional blocks may be referred to in describingsome embodiments. Generally, functional blocks include one or moreinterrelated circuits, devices, and/or mechanisms that perform describedoperations. In some embodiments, at least some of the functional blocksinclude general-purpose processing circuits that execute program code(e.g3, microcode, firmware, applications, etc.) that causes thegeneral-purpose processing circuits to perform the described operations.

Overview

The described embodiments transfer an activity performed at a sourceelectronic device from the source electronic device to a companionelectronic device—a process that is referred to as “continuing” theactivity in the companion electronic device. In the describedembodiments, to perform the transfer, the source electronic device sendsinformation that describes an activity performed in a first applicationat the source electronic device to the companion electronic device. Thecompanion electronic device then uses some or all of the information toconfigure a second application at the companion electronic device toperform a corresponding activity. Generally, the activity includes oneor more operations that are performed at least partially at the sourceelectronic device that are transferred to/continued on the companionelectronic device. Examples of activities include reading and/or editinga document (e.g., a word processing document, spreadsheet, presentation,or other type of document), composing an email message, an email, voicemessage or video, drafting a note, accessing (browsing) a website,watching a movie, playing an audio file, or otherwise using anapplication or app to perform corresponding operations.

In some embodiments, when transferring an activity from the sourcedevice to the companion device, the source electronic device firstbroadcasts an activity advertisement message (also referred to as an“activity advertisement”) using a wireless network interface (e.g.,Bluetooth low energy (BLE,), ZigBee, etc.), in some embodiments, thesource electronic device generates an activity identifier for theactivity performed in a first application at the source electronicdevice and includes the activity identifier in the activityadvertisement message. The source electronic device generates theactivity identifier by performing a set of operations (e.g., a hashoperation, etc.) using activity information that describes the activitythat is received from the first application. Examples of activityinformation are described in more detail below with reference to FIG.11.

The companion electronic device monitors a network (e.g., a Bluetoothlow energy network) for activity advertisement messages on a networkinterface corresponding to the network interface in the sourceelectronic device from which the activity advertisement was broadcast.Upon detecting the activity advertisement broadcast from the sourceelectronic device, the companion electronic device compares activityidentifiers for activities that are available at the companionelectronic device to the activity identifier in the activityadvertisement message. The companion electronic device uses thiscomparison to determine whether a second application that can perform anactivity corresponding to the activity performed in the firstapplication is available at the companion electronic device.

In some embodiments, upon determining that the second application isavailable, the companion electronic device establishes communicationwith the source electronic device over a communication channel (e.g.,using the same wireless network interface used to receive the activityadvertisement message or a different network interface, wireless and/orwired). The companion electronic device then uses the communicationchannel to request extended activity data for the activity performed inthe first application from the source electronic device. In someembodiments, upon receiving the request for extended activity data, thesource electronic device uses the same (or a different) communicationchannel to provide the extended activity data to the companionelectronic device. Generally, the extended activity data includesinformation that can be used to configure the second application in thecompanion electronic device to continue the activity, such as a documentidentifier, a scroll position, a uniform resource locator (URL), etc.related to the activity performed in the first application.

In some embodiments, the companion electronic device uses the activityidentifier and/or the extended activity data to configure the secondapplication to perform an activity corresponding to the activityperformed in the first application at the source electronic device.Then, the companion electronic device starts performing the activity inthe second application at the companion electronic device. For example,after the companion electronic device configures the second application,a user can use the companion electronic device to continue working on adocument that the user was working with at the source electronic device,to continue watching a movie that the user was watching at the sourceelectronic device, to continue browsing a webpage that the user wasbrowsing at the source electronic device, etc. In some embodiments, thecompanion electronic try device sends a notification to the sourceelectronic device to indicate that the activity was transferred to thesecond application. The notification can cause the source electronicdevice and/or the first application to perform housekeeping tasks, suchas deleting a document draft for the activity, closing an open documentfor the activity, etc.

By performing the operations described above for continuing an activityperformed at the source electronic device at the companion electronicdevice, the described embodiments enable a user to continue a taskseamlessly and without complex user intervention. This enables the userto more easily perform tasks on desired electronic devices, which canimprove the user's overall experience with two or more electronicdevices.

Electronic Device

FIG. 1 presents a block diagram illustrating electronic device 100 inaccordance with some embodiments. Electronic device 100 includesprocessing subsystem 102, memory subsystem 104, networking subsystem106, and display subsystem 108.

Processing subsystem 102 is a functional block that performscomputational operations in electronic device 100. Processing subsystem102 includes one or more central processing units (CPUs)/CPU cores,graphics processing units (GPUs)/GPU cores, embedded processors,application specific integrated circuits (ASICs), and/or othercomputational mechanisms.

Memory subsystem 104 is a functional block that stores data and/orinstructions for use by other functional blocks in electronic device 100(e.g., processing subsystem 102, etc.). Memory subsystem 104 includesvolatile memory circuits such as dynamic random access memory (DRAM),static random access memory (SRAM), and/or other types of memory thatare used for storing the instructions and data, as well as mechanismsfor controlling the memory circuits. In some embodiments, memorysubsystem 104 includes a memory hierarchy with one or more cachescoupled to the memory circuits. In some of these embodiments, processingsubsystem 102 also includes one or more caches that are part of thememory hierarchy.

In some embodiments, memory subsystem 104 is coupled to one or morenon-volatile high-capacity mass-storage devices (not shown). Forexample, memory subsystem 104 can be coupled to a magnetic or opticaldrive, a solid-state drive, or another type of mass-storage device. Inthese embodiments, memory subsystem 104 can be used by electronic device100 as fast-access storage for often-used data, while the mass-storagedevice is used to store less frequently used data.

Networking subsystem 106 is a functional block that includes one or moredevices configured to couple to and communicate on a wired and/orwireless network (i.e., to perform network operations). For example,networking subsystem 106 can include a Bluetooth™ networking system, acellular networking system (e.g., a 3G/4G network such as UNITS, LTE,etc.), a universal serial bus (USB) networking system, a networkingsystem based on the standards described in IEEE 802.11, 802.15, etc.(e.g., a ZigBee or Wi-Fi networking system, etc.), an Ethernetnetworking system, and/or another networking system. Networkingsubsystem 106 includes processors, controllers, radios/antennas,sockets/plugs, and/or other devices used for coupling to, communicatingon, and handling data and events for each supported networking system.In the following description, the mechanisms used for coupling to,communicating on, and handling data and events on the network for eachnetwork system are referred to collectively as the “interface” or“network interface” for the network system.

Display subsystem 108 is a functional block that includes one or moredevices configured to display information on a visual interface forelectronic device 100. For example, in some embodiments, displaysubsystem 108 includes graphics processors (CPUs), graphics cards,and/or display screens that are used for displaying the information.

In some embodiments, communication paths (that include one or morebuses, wires, and/or connections) are coupled between the functionalblocks in electronic device 100 (processing subsystem 102, memorysubsystem 104, etc.), as shown by arrow-headed lines between theelements. The communication paths are used to transmit commands, data,event notifications, and/or other information between the elements.

Although specific components are used to describe electronic device 100,in some embodiments, different components and/or subsystems may bepresent in electronic device 100. For example, electronic device 100 mayinclude one or more additional processing subsystems 102, memorysubsystems 104, etc. Additionally, one or more of the subsystems may notbe present in electronic device 100 or some or all of the subsystem'sfunctions may be incorporated in the other subsystems. Moreover, in someembodiments, electronic device 100 may include one or more additionalsubsystems that are not shown in FIG. 1. For example, electronic device100 can include, but is not limited to, a data collection subsystem, anaudio and/or video subsystem, an alarm. subsystem, a media processingsubsystem, and/or an input/output (I/O) subsystem.

Electronic device 100 can be, or can be included in, any device thatperforms computational operations. For example, electronic device 100can be, or can be included in, a desktop computer, a laptop computer, awearable computing device, a tablet computer, a smart phone, a server, anetwork appliance, a toy, audio-visual equipment (e.g., a receiver, settop box, Apple TV, etc.), automobiles (e.g., a car interface system,navigation system, heads-up display, etc.), home appliances,controllers, etc., and/or combinations thereof. (Apple TV is aregistered trademark of Apple Inc. of Cupertino, Calif.).

Network Environment

FIG. 2 presents a block diagram illustrating a network environment inaccordance with some embodiments. As can be seen in FIG. 2, networkenvironment 200 includes source electronic device 202, companionelectronic device 204, and second source electronic device 206 (referredto collectively as “the electronic devices”). In some embodiments, eachof the electronic devices is an electronic device similar to electronicdevice 100, i.e., has similar subsystems to electronic device 100.However, this is not required; the described embodiments can use anyelectronic devices that can perform the operations herein described.

Source electronic device 202 and second source electronic device 206 areelectronic devices that participate in exchanges of communications withcompanion electronic device 204 relating to activity transferoperations. In some embodiments, source electronic device 202 (and/orsecond source electronic device 206) is an electronic device that isrecognized by companion electronic device 204 and therefore is allowedto participate in an activity transfer operation. For example, bothsource electronic device 202 and companion electronic device 204 mayhave been registered with a service provider using the same account andmay therefore recognize each other via information stored in eachelectronic device. For example, in some embodiments, source electronicdevice 202 and companion electronic device 204 participate in (andrecognize each other via information acquired through) a preliminarypairing operation, e.g., a predefined pairing, as described in pendingU.S. patent application Ser. No. xx/xxx,xxx, which is titled “PredefinedWireless Pairing,” by inventors Jason C. Conn, Akshay Mangalam Srivatsa,Craig P. Dooley, and Michael Giles, filed on the same day as the instantapplication, which has attorney docket no. APL-P22642USP1, and thecontents of which are incorporated by reference as described above. Insome embodiments, source electronic device 202 and companion electronicdevice 204 may participate in a device-to-device exchange ofidentification factors (encryption keys, certificates, etc.) so thatsource electronic device 202 and companion electronic device 204subsequently recognize each other.

Within network environment 200, companion electronic device 204 cancommunicate with source electronic device 202 and second sourceelectronic device 206 using wireless communication signals 208(illustrated using jagged lines labeled “COMMUNICATION SIGNALS 208” inFIG. 2). In some embodiments, communication signals 208 are formattedand exchanged (broadcast, transmitted/received., etc.) in accordancewith a corresponding wireless protocol—for example, via a wirelessnetwork protocol such as Bluetooth, ZigBee, an 802.11-based protocoland/or other wireless network protocols. In some embodiments, some orall of communication signals 208 are communicated as wired communicationsignals, e.g., signals in wired Ethernet, a wired LAN, a wired WAN, etc.

In some embodiments, the activity transfer operations described hereinrely on source electronic device 202 and companion electronic device 204being sufficiently close to each other to enable communication signals208 (and thus the incorporated messages) sent by each electronic deviceto be received by the other electronic device. In other words, sourceelectronic device 202 and companion electronic device 204 are in“proximity” to one another, thereby enabling die exchange of messagesbetween the electronic devices. “Proximity” as used herein thereforerepresents distance(s) at which messages broadcast/sent from a givenelectronic device can be received by one or more other electronicdevices. This distance is dictated by radio equipment (antennas,receivers/transmitters, etc.) in the electronic devices and theparticular radio protocol/signals used to broadcast/send the messages,as limited by factors such as environmental conditions (electromagneticinterference, etc.), intermediate objects (furniture, walls,clothing/bags, etc.), etc. For example, in some embodiments,communication signals 208 are exchanged between source electronic device202 and companion electronic device 204 using a protocol with anexpected range of 30 meters, and thus the devices are “in proximity”when the devices are within 30 meters of one another (note, however,that the expected range may be significantly altered by theabove-described factors).

FIG. 16 presents a block diagram illustrating electronic devices inproximity to one another in accordance with some embodiments. As can beseen in FIG. 16, companion electronic device 204 is within range 1602for radio signals (e.g., communication signals 208) for sourceelectronic device 202, meaning that companion electronic device 204 canreceive radio signals sent from source electronic device 202. Inaddition, source electronic device 202 is within range 1604 for radiosignals (e.g., communication signals 208) for companion electronicdevice 204, meaning that source electronic device 202 can receive radiosignals sent from companion electronic device 204. As described above,therefore, source electronic device 202 and companion electronic device204 are “in proximity” to one another, thereby enabling thecommunication of messages (and corresponding operations) hereindescribed. However, neither source electronic device 202 nor companionelectronic device 204 is within range 1606 for radio signals forelectronic device 1600, meaning that neither source electronic device202 nor companion electronic device 204 is in proximity to electronicdevice 1600. Note that ranges 1602-1606 in FIG. 16 are shown usingirregular shapes, thereby illustrating that radio signals from theelectronic devices have irregular ranges, depending on the electronicdevice (antenna arrangement, etc.), the above-described factors, etc.

In some embodiments, the messages, data, etc. communicated between theelectronic devices are encrypted. In these embodiments, some or all ofthe electronic devices perform corresponding encryption and decryptionoperations, e.g., by using a shared key, keys derived from a shared key,and/or a one-time key. For example, as described earlier, in someembodiments, source electronic device 202 and companion electronicdevice 204 participate in a predefined pairing as described in pendingU.S. patent application Ser. No, xx/xxx,xxx, which is titled “PredefinedWireless Pairing,” by inventors Jason C. Conn, Akshay Mangalam Srivatsa,Craig P. Dooley, and Michael Giles, filed on the same day as the instantapplication, which has attorney docket no. APL-P22642USP1, and thecontents of which are incorporated by reference as described above. Insome embodiments, source electronic device 202 and companion electronicdevice 204 encrypt and decrypt messages exchanged for activity transferoperations by using one or more encryption keys that source electronicdevice 202 and companion electronic device 204 acquire whileparticipating in the predefined pairing.

Although various electronic devices ate shown in FIG. 2, in someembodiments different arrangements of electronic devices are used toperform some or all of the operations herein described. For example, insome embodiments, second source electronic device 206 is not present.Generally, the described embodiments include sufficient devices totransition an activity between electronic devices as described herein.

Broadcasting an Activity Advertisement Message

FIG. 3 presents a flowchart illustrating a process for broadcasting anactivity advertisement message in accordance with some embodiments. Morespecifically, during the process shown in FIG. 3, an electronic devicesuch as source electronic device 202 broadcasts an activityadvertisement message. Note that the operations shown in FIG. 3 arepresented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., source electronic device 202, etc.), in someembodiments, other mechanisms perform the operations. For example, oneor both of companion electronic device 204 and second source electronicdevice 206 may perform similar operations to broadcast an activityadvertisement message for themselves.

The process shown in FIG. 3 starts when source electronic device 202receives activity information that describes an activity performed in afirst application at source electronic device 202, i.e., a firstapplication installed on/available at source electronic device 202 (step300). (Examples of activity information are described in more detailbelow with reference to FIG. 11). In some embodiments, the firstapplication provides or reports the activity information to sourceelectronic device 202, e.g., provides or reports the activityinformation to an operating system, a daemon, or other process and/orservice at source electronic device 202. In some embodiments, sourceelectronic device 202 queries the first application for the activityinformation. Generally, activity information includes information thatdescribes an activity performed at least partially using an electronicdevice. Examples of activities include reading and/or editing a document(e.g., a word processing document, spreadsheet, presentation, or othertype of document), composing an email message, drafting a note,accessing (browsing) a website, watching a movie, playing an audio file,or otherwise using an application or app to perform correspondingoperations.

Next, source electronic device 202 determines whether to filter thereceived activity information (step 302), which includes using one ormore criteria to discard activity information that is not to undergofurther processing and/or not to be broadcast in an activityadvertisement message. For example, source electronic device 202 maymeasure a frequency at which the first application provides updates tothe activity information, and may discard activity information from thefirst application when the frequency at which the activity informationis updated exceeds a threshold (which may be referred to as “throttling”the activity information from the first application). As anotherexample, source electronic device 202 may discard activity informationthat is duplicative or repetitive, that does not contain significantchanges to previously reported activity information (e.g., automaticreports of “no change,” reports of simple/basic operations/changes,etc.), that reports facts already known by source electronic device 202,etc. As yet another example, in some embodiments, source electronicdevice 202 filters the activity information based on an indication thatan activity described by the activity information is not to beadvertised. For example, in some embodiments, source electronic device202 and/or a user of source electronic device 202 may configure certainactivities and/or certain kinds of activities as activities that are notto be advertised. As yet another example, in some embodiments, sourceelectronic device 202 ranks some or all activities for which activityinformation exists (i.e., some or all of the activities that can beadvertised) and discards one or more of these activities based on theranking. For example, source electronic device 202 can assign a higherranking to activities that a user has previously continued and a lowerranking to activities that a user has previously not continued. In someof these embodiments, source electronic device 202 uses messages fromcompanion electronic device 204 to determine which advertised activitieswere previously continued and which advertised activities werepreviously not continued, e.g., messages such as those described belowwith reference to FIG. 5, step 510.

If source electronic device 202 filters, e.g., discards, the activityinformation (step 302, yes), the process ends. Otherwise, if sourceelectronic device 202 does not filter the activity information (step302, no), source electronic device 202 stores some or all of theactivity information in a structure (step 304). For illustrativepurposes, we describe embodiments that store the activity information inan entry in a table, which we will refer to as the “advertised-activity”table. Note, however, that embodiments are not limited to using a tablefor storing activity information. Some embodiments use a differentstorage mechanism/structure for storing the activity information, suchas an associative array, a content-addressable memory, etc.

In some embodiments, while storing the activity information, sourceelectronic device 202 overwrites and/or removes activity informationpreviously stored in the advertised-activity table. For example, sourceelectronic device 202 can use a least-recently-used (LRU) algorithm tooverwrite and/or remove entries from the advertised-activity table.Examples of advertised-activity tables are described in more detailbelow with reference to FIG. 12.

Next, source electronic device 202 determines an activity identifier forthe activity information (step 306). Generally, the activity identifierincludes information from the activity information that identifies thefirst application and the activity performed in the first application.In some embodiments, source electronic device 202 generates the activityidentifier by reducing the activity information into a smaller, encodedrepresentation that can be broadcast more efficiently than the fullactivity information. In some of these embodiments, the encodedrepresentation is a hash of the activity information, i.e., the outputof a hash function (e.g., MD4, MD5, SHA, MurmurHash, etc.) whose inputcomprises the activity information. In some embodiments, sourceelectronic device 202 stores the activity identifier along with theactivity information in the advertised-activity table (or whateverstructure source electronic device 202 uses to store the activityinformation). Examples of activity identifiers are described in moredetail below with reference to FIG. 12.

In some embodiments, the activity identifier comprises a representationof a domain name. For example, in some embodiments, when the activityperformed in the first application includes using a resource at adomain, the activity information comprises a domain name, e.g., at leasta portion of a uniform resource locator (URL), of the domain. In someembodiments, source electronic device 202 determines the activityidentifier by including some or all of the domain name in the activityidentifier. For example, the activity identifier can be a hash of someor all of the URL for the resource.

In some embodiments, the activity identifier identifies an entry in astructure where source electronic device 202 stored the activityinformation (e.g., as described above with reference to step 304). Forexample, the activity identifier can identify the entry in theadvertised-activity table where source electronic device 202 stored theactivity information. The activity identifier can also include anidentifier for the advertised-activity table itself. In someembodiments, to identify the entry in the structure where sourceelectronic device 202 stored the activity information, the activityidentifier includes: (1) a hash of the data in the advertised-activitytable to identify the advertised-activity table, and (2) an index forthe entry in the advertised-activity table that stores the activityinformation.

Source electronic device 202 next includes the activity identifier intoan activity advertisement message (step 308). In some embodiments, theactivity advertisement message includes other data in addition to theactivity identifier. For example, in some embodiments, the activityadvertisement message includes a flag that is used to indicate when theactivity identifier includes a representation of domain name for anonline resource related to the activity. In these embodiments, sourceelectronic device 202 asserts the flag (e.g., sets the flag to apredetermined value such as 1) to indicate that the activity identifierincludes a representation of a domain name. In some embodiments, sourceelectronic device 202 asserts a flag in the activity advertisementmessage to indicate that the advertised activity can be continued in away that source electronic device 202 will separately provide tocompanion electronic device 204, e.g., by source electronic device 202including corresponding instructions in the extended activity data(extended activity data is described in more detail below).

In some embodiments the activity advertisement message includes atimestamp for the activity/activity information. The timestamp, whichcan express an absolute time or a relative time, can indicate the timethat the activity was last performed in the first application, e.g., thelast time that a document was edited, a website was accessed, a moviewatched, etc. In some embodiments the timestamp is independent of theactivity/activity information, i.e., the timestamp indicates the timethat a user last interacted with source electronic device 202,regardless of whether the user's last interaction included the userperforming the activity.

Source electronic device 202 then broadcasts the activity advertisementmessage (step 310). For example, source electronic device 202 canbroadcast the activity advertisement message using communication signals208. In some embodiments, source electronic device 202broadcasts/advertises the activity advertisement message in networkenvironment 200 so that nearby devices in network environment 200 canreceive the activity advertisement message. For example, in theseembodiments, source electronic device 202 uses a Bluetooth™communication channel such as Bluetooth Low Energy (BLE) to broadcastthe activity advertisement message. Some embodiments may broadcast theactivity advertisement message on a different communication channel,such as a peer-to-peer network, a LAN, the Internet, etc. Note thatactivity broadcasts can happen more than once, e.g., source electronicdevice 202 can broadcast the same activity advertisement messagemultiple times and/or periodically.

Building an Available-Activity Table

In some embodiments, companion electronic device 204 stores availableactivity information, e.g., activity information describing activitiesthat are available at companion electronic device 204 (examples ofactivity information are described in more detail below with referenceto FIG. 11). For example, in some embodiments, companion electronicdevice 204 stores activity identifiers for the available activityinformation. For illustrative purposes, we describe companion electronicdevice 204 storing the available activity information in a table, whichwe refer to as the “available-activity” table (examples ofavailable-activity tables are described in more detail later in thisdisclosure). Note that, although we describe embodiments that storeavailable activity information in an available-activity table,embodiments are not limited to using a table for storing the availableactivity information. Some embodiments can use other structures forstoring the available activity information, such as an associativearray, a content-addressable memory, etc.

FIG. 4 presents a flowchart illustrating a process for storing activityinformation describing activities that are available at companionelectronic device 204 into an available-activity table in accordancewith some embodiments. Note that the operations shown in FIG. 4 arepresented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., companion electronic device 204, etc.), in someembodiments, other mechanisms perform the operations. For example, oneor both of source electronic device 202 and second source electronicdevice 206 may perform similar operations to store available activityinformation describing activities that are available for themselves.

The process shown in FIG. 4 starts when companion electronic device 204receives activity information describing an activity that is availableat a second application at companion electronic device 204 (step 400),e.g., activity information describing activities that can be performedat companion electronic device 204. Generally, this activity informationdescribes an activity that can be performed in the second application atcompanion electronic device 204, i.e., an operation or function that thesecond application at companion electronic device 204 is able toperform. In some embodiments, the second application reports/providesthe activity information as the second application is installed and/orused. In some embodiments, companion electronic device 204 queries orotherwise monitors the second application to collect the activityinformation that describes the activity that is available at the secondapplication. In some embodiments, the activity information includesactivity information for activities that have not been performed oncompanion electronic device 204, but that are available to be performed(e.g., activity information reported by the second application as thesecond application is installed/updated, launched, used, etc. atcompanion electronic device 204).

Next, companion electronic device 204 determines a second activityidentifier, i.e., an activity identifier for the activity informationthat describes the activity that is available at the second application(step 402). Generally, the second activity identifier identifies thesecond application and the activity that is available at the secondapplication. The second activity identifier can be an encodedrepresentation of the activity information that describes the activitythat is available at the second application. In some embodiments,companion electronic device 204 determines the second activityidentifier by performing some or all of the same operations that sourceelectronic device 202 performs to generate the activity identifier forthe activity performed in the first application (see FIG. 3, step 306).For example, in some embodiments companion electronic device 204 usesthe same hash function to generate the second activity identifier thatsource electronic device 202 uses to generate the activity identifierfor the activity performed in the first application.

In some embodiments, when the second application can perform an activitythat includes accessing a resource at a domain, the activity informationfor this activity includes a domain name for the domain. In some ofthese embodiments, the second activity identifier is an encodedrepresentation of the domain name, which enables the second applicationto “claim” the domain name, i.e., to declare that the second applicationcan use resources at the domain name so that companion electronic device204 can transfer corresponding activities to the second application. Forexample, as will be described later, in a scenario where the secondapplication streams movies from a specific site on the Internet, thesecond activity identifier can be an encoded representation of at leastsome part of the domain name for the site. Note that the secondapplication can be different from the first application, i.e., theapplication whose activity is advertised in the activity advertisementmessage, enabling an application different from the first application tocontinue the activity at companion electronic device 204.

Next, companion electronic device 204 stores the second activityidentifier into the available-activity table (step 404).

Requesting Extended Activity Data and Transferring Activity

In some embodiments, upon receiving an activity advertisement message,an electronic device can request extended activity data for theadvertised activity so that the advertised activity can subsequently betransferred to the electronic device. FIG. 5 presents a flowchartillustrating a process for requesting extended activity data andtransferring an activity in accordance with some embodiments. Morespecifically, during the process shown in FIG. 5, companion electronicdevice 204 requests, from source electronic device 202, extendedactivity data for an activity performed in a first application in sourceelectronic device 202. Note that the operations shown in FIG. 5 arepresented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., source electronic device 202, companion electronicdevice 204), in some embodiments, other electronic devices and/ormechanisms perform the operations.

The process shown in FIG. 5 starts when companion electronic device 204receives an activity advertisement message (step 500), e.g., theactivity advertisement message broadcast from source electronic device202 (see FIG. 3, step 310). Next, companion electronic device 204determines whether companion electronic device 204 is in a receptivestate (step 502). Generally, companion electronic device 204 is in areceptive state when it is available for performing an activitytransfer. For example, in some embodiments, companion electronic device204 transitions to a receptive state when the device “wakes-up,” e.g.,while displaying a lock screen after a user presses a button to wake-upthe device. In some embodiments, companion electronic device 204 is notin a receptive state when companion electronic device 204 is in use,e.g., when a user is using an application at companion electronic device204 and/or when the user has used an application within a given periodof time.

If companion electronic device 204 is not in a receptive state (step502, no), the process ends (i.e., the activity advertisement message isignored). Otherwise, if companion electronic device 204 is in areceptive state (step 502, yes), companion electronic device 204determines whether a second application that is associated with thefirst application is available at companion electronic device 204 (step504). Generally, this operation includes determining if an applicationis available on companion electronic device 204 for continuing theactivity described in the activity advertisement message from sourceelectronic device 202. Determining whether the second application isavailable is described in more detailed later with reference to FIGS.7-8.

If the second application is not available (step 504, no), the processends. Otherwise, if the second application is available (step 504, yes),companion electronic device 204 retrieves activity information for thesecond application (step 506). For example, as will also be described inmore detail with reference to FIGS. 7-8 and 11-12, after determining thesecond application, companion electronic device 204 can use the activityidentifier for the second application to retrieve activity informationthat describes the activity that is available in the second applicationfrom the available-activity table (or from another structure thatcompanion electronic device 204 uses to store available activityinformation). In some embodiments, companion electronic device 202 usesthe retrieved activity information, e.g., uses an application identifierin the retrieved activity information, to customize an indication thatthe activity is resumable, e.g., as described below with reference tostep 508 and/or FIG. 14. Application identifiers are described in moredetail with reference to FIG. 11.

Next, companion electronic device 204 presents an indication that theactivity is resumable (step 508). For example, companion electronicdevice 204 can present a graphical icon and/or notification in a displayof companion electronic device 204. Indications are described in moredetail below with reference to FIG. 14.

Then, companion electronic device 204 determines whether the activitytransfer was accepted (step 510). In some embodiments, a user ofcompanion electronic device 204 accepts and/or rejects the activitytransfer by performing an action with the indication, such as clickingon the indication, dragging the indication in one or more directionsand/or to one or more specific locations, etc. For example, to acceptthe activity transfer, a user can tap the icon/notification with afinger (on a touch screen display) and drag the icon/notification in afirst direction (e.g., left to right, upward, clockwise in a circle,etc.). As another example, to reject an activity, a user can tap theicon/notification with a finger and drag the icon/notification in asecond direction (e.g., right to left, downward, counterclockwise in acircle, etc.). In sonic embodiments, companion electronic device 204determines that the activity transfer was not accepted based on atime-out period, i.e., by determining that a period of time has passedsince the indication was presented without the user performing theaction to accept the indication/activity transfer.

If the activity transfer is not accepted (step 510, no), the processends. Note that, in some embodiments, if the activity transfer is notaccepted, companion electronic device 204 sends a message to sourceelectronic device 202 to indicate that the activity transfer was notaccepted. If the activity transfer is accepted (step 510, yes),companion electronic device 204 sends a message to source electronicdevice 202 to request extended activity data for the activity performedin the first application (step 512). Generally, the request for extendedactivity data includes information to facilitate source electronicdevice 202 determining the activity for which the extended data is beingrequested. For example, in some embodiments companion electronic device204 includes the activity identifier from the activity advertisementmessage with the request for extended activity data.

Next, upon receiving extended activity data from source electronicdevice 202 in response to the request for extended activity data,companion electronic device 204 configures the second application usingthe extended activity data (step 514). Configuring the secondapplication can include launching/starting the second application,setting a state (or causing a change to the state) of the secondapplication based on the extended activity data, and otherwiseconfiguring the second application to perform a corresponding operation.For example, companion electronic device 204 can pass adocument/resource identifier, information representing thedocument/resource, and/or a reference to the document/resource in theextended activity data to the second application to cause the secondapplication access to the document/resource (e.g., an identifierfor/information representing/a reference to a cloud-stored document forthe second application to access from cloud-based storage located on theInternet, an identifier for/information representing/a reference to adocument for the second application to access from a database, etc.). Insome embodiments, when the activity includes composing a document thatis stored at source electronic device 202, the extended activity dataincludes the document or information representing the document, therebyenabling companion electronic device 204 and/or the second applicationto use/re-create the document at companion electronic device 204 for thesecond application. In some embodiments, the extended activity dataincludes edits in a document, e.g., the position and/or content of editsmade in a document. In some embodiments, the extended activity dataincludes position information, such as the last played/viewed/recordedposition in a media file (i.e., the position in the media file whereplayback or recording stopped or was last performed), the position of amarker in a file, the position/state of gameplay in a video game (e.g.,the last level played, coordinates to a place that the player was lastat, points and/or achievements earned, and/or information that can beused to recreate the state of a game played on source electronic device202 at companion electronic device 204), etc.

Then, companion electronic device 204 commences performing the activityin the second application (step 516), which generally includesstarting/launching the second application at companion electronic device204 (if the second application was not already running) and executingthe second application at companion electronic device 204 based on theextended activity data. For example, companion electronic device 204 cancause the second application to start executing in a viewing and/orediting mode for the document related to the advertised activity, andcan cause the second application to scroll to the last position in thedocument that the document was viewed/edited at source electronic device202. Next, companion electronic device 204 sends a notification tosource electronic device 202 indicating that the activity wastransferred (step 518).

Note that some embodiments can use information in the activityadvertisement message, e.g., the activity identifier, to startconfiguring the second application while the extended activity data isbeing transmitted, or even before the extended activity data isrequested. Some of these embodiments use the information in the activityadvertisement message to set an initial background for the secondapplication, to set a mode for the second application (e.g., an editingmode, a read-only mode, an email composition mode, a note compositionmode, etc.). Hence, some embodiments can launch and/or configure thesecond application before the extended activity data is received,possibly as soon as the activity transfer is accepted, thereby improvingperformance in slow networks by hiding data transfer time withapplication launch time.

In some embodiments, companion electronic device 204 sends the requestfor extended activity data using different signals than communicationsignals 208, and/or by using a different communication channel/networkinterface than the one the activity advertisement message was receivedon. For example, companion electronic device 204 can receive theactivity advertisement message over a Bluetooth link (using the BLEprotocol) and can request the extended activity data over a Wi-Fi linkor the Internet. In these embodiments, source electronic device 202 andcompanion electronic device 204 use communication signals 208, e.g., theBluetooth link, to exchange information that enables the electronicdevices to communicate over the different communication channel/network.For example, in some of these embodiments, companion electronic device204 creates a peer-to-peer network (e.g., an ad-hoc Wi-Fi network) andprovides information to access the peer-to-peer network to sourceelectronic device 202. In some embodiments, source electronic device 202provides the extended activity data to a server and companion electronicdevice 204 receives the extended activity data from the server, e.g.,through the Internet.

Transitioning to a Receptive State Based on Advertising Information

Although in FIG. 5 we describe embodiments that receive an activityadvertisement message (FIG. 5, step 500) and determine whether companionelectronic device 204 is in a receptive state (FIG. 5, step 502), someembodiments transition to a receptive state based on information inreceived activity advertisement messages. In some of these embodiments,after receiving an activity advertisement message (e.g., as shown inFIG. 5, step 500), companion electronic device 204 does not determinewhether companion electronic device 204 is in a receptive state, i.e.,the process shown in FIG. 5 proceeds from step 500 to step 504 withoutperforming operations for step 502.

For example, in some embodiments, source electronic device 202 uses alow-power protocol such as Bluetooth low-energy (BLE), ZigBee, etc. tobroadcast the activity advertisement message with correspondingcommunication signals 208. Devices such as companion electronic device204 may monitor for activity advertisement messages broadcast fromsource electronic device 202 using corresponding low-power mechanisms,such as a baseband processor within a corresponding network interface,e.g., a baseband processor in networking subsystem 106. In some of theseembodiments, the receiving of the activity advertisement message ishandled by companion electronic device 204 using only a basebandprocessor for companion electronic device 204, which means thatcompanion electronic device 204 may otherwise be in an idle state (e.g.,with subsystems such as the processing subsystem in a low-power state).For example, in some embodiments, companion electronic device 204 may bea smart phone in a user's pocket in an idle state in which a basebandprocessor monitors for activity advertisement messages while theprocessing subsystem (and companion electronic device 204 generally) isin a low-power state.

In some embodiments, upon recognizing the activity advertisement messageas such, the baseband processor wakes the processing subsystem (and maygenerally transition companion electronic device 204 out of the idleoperating state to a higher-power/more active operating state) toperform subsequent operations. For example, in some embodiments,companion electronic device 204 may monitor for activity advertisementmessages and react to activity advertisement messages as is described inpending U.S. patent application Ser. No. xx/xxx,xxx, which was filed onthe same day as the instant application, which is titled “Operating ModeTransitions based on Advertising Information,” by inventors Craig P.Dooley, Akshay Mangalam Srivatsa, Anjali S. Sandesara, and MichaelGiles, which has attorney docket no. APL-P22643USP1, and which isincorporated by reference as described above. In some embodiments,companion electronic device 204/the smart phone may not need to beretrieved from the user's pocket and activated to place companionelectronic device 204 in a receptive state.

Responding to a Request for Extended Activity Data

FIG. 6 presents a flowchart illustrating a process for responding to arequest for extended activity data in accordance with some embodiments.More specifically, during the process shown in FIG. 6, an electronicdevice such as source electronic device 202 responds to a request forextended activity data from an electronic device such as companionelectronic device 204. Note that the operations shown in FIG. 6 arepresented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., source electronic device 202, companion electronicdevice 204), in some embodiments, other electronic devices and/ormechanisms perform the operations.

The process shown in FIG. 6 starts when source electronic device 202receives a request for extended activity data (step 600), e.g., therequest for extended activity data that companion electronic device 204transmitted, as described with reference to step 512 in FIG. 5.

Next, source electronic device 202 uses information in the request forextended activity data to determine that the request is for extendedactivity data for the first application (step 602). For example, asdescribed earlier, the request for extended activity data can includethe activity identifier from the activity advertisement message (seestep 308 in FIG. 3). In some embodiments, source electronic device 202performs a lookup for the activity identifier in the advertised-activitytable (or other structure where advertised activity information isstored; examples of advertised-activity tables are described in moredetail below with reference to FIG. 12). When source electronic device202 finds an entry in the advertised-activity table that includes theactivity identifier from the activity advertisement message, sourceelectronic device 202 can retrieve the activity information for theentry to determine that the activity identifier corresponds to the firstapplication, e.g., by determining that the application identifier forthe entry is the application identifier for the first application(examples of activity information and application identifiers aredescribed in mote detail with reference to FIGS. 11-12).

Next, source electronic device 202 optionally sends anotification/request to the first application to perform an updaterelated to the activity (step 604). In some embodiments, thenotification causes the first application to update the extendedactivity data before providing the extended activity data to companionelectronic device 204. For example, the first application can use thenotification to update the last scroll/viewed position for a documentrelated to the activity and/or to perform finalizing operations relatedto the activity before the activity is transferred, such as saving adocument related to the activity, updating the extended activity datawith the latest draft of a document related to the activity, etc.

Then, source electronic device 202 retrieves the extended activity datafor the first application (step 606). In some embodiments, sourceelectronic device 202 requests that the first application provide theextended activity data. In some embodiments, the first applicationprovides some or all of the extended activity along with the initialactivity information (see FIG. 3, step 300) and/or periodically reportsextended activity information. (e.g., reports every N seconds, where Nis a number such as 1, 3, etc., reports extended activity informationeach time an event happens for the first application, such as when adocument is saved in the first application, a movie being watched ispaused in the first application, etc.).

Next, source electronic device 202 sends the extended activity data tocompanion electronic device 204 (step 608). Generally, the extendedactivity data includes information that can be used to configure thesecond application to continue the activity, such as a documentidentifier that identifies a document used for the activity performed inthe first application (and/or information representing the document,such as a reference to the document), a uniform resource location (URL)of web page accessed/browsed in the first application (and/orinformation representing the web page/URL, such as a reference to theweb page/URL), position information (e.g., an indication of the lastviewed/scrolled position in the document or the web page, the lastplayed position in a video game, etc.), a copy of a draft documentstored at source electronic device 202 and/or in a storage deviceaccessible on the Internet (e.g., “cloud storage”) or a corporatenetwork (and/or information representing the draft document, such as areference to the draft document), etc.

Then, source electronic device 202 receives a notification that theactivity was transferred (step 610), e.g., receives the notificationsent by companion electronic device 204 as described with reference toFIG. 5, step 518. In some embodiments, in response to receiving thenotification, source electronic device 202 notifies the firstapplication that the activity was transferred (step 612). In someembodiments, source electronic device 202 and/or the first applicationperforms one or more operations related to the activity based onreceiving the notification, e.g., housekeeping tasks such as deleting alocally-stored document/document draft, closing an open document,shutting down the application, etc.

In some embodiments, source electronic device 202 provides the extendedactivity data using different signals than communication signals 208,and/or by using a different communication channel/network interface thanthe one the activity advertisement message and/or the request forextended activity data was communicated on. For example, sourceelectronic device 202 can receive the request for extended activity dataover a Bluetooth link and can provide the extended activity data over aWi-Fi link or the Internet.

Secure Communication Using Cloud Pairing

As discussed earlier, in some embodiments, electronic devices thatperform activity transfer operations participate in a preliminarypairing operation, e.g., a “cloud pairing” operation, such as thepredefined pairing described in pending U.S. patent application Ser. No.xx/xxx,xxx, which is titled “Predefined Wireless Pairing,” by inventorsJason C. Conn, Akshay Mangalam Srivatsa, Craig P. Dooley, and MichaelGiles, filed on the same day as the instant application, which hasattorney docket no. APL-P22642USP1, and the contents of which areincorporated by reference as described above. In some embodiments,electronic devices encrypt and decrypt messages exchanged with eachother for performing activity transfer operations using securityinformation acquired during the cloud pairing operation, e.g., usingencryption keys acquired during the cloud pairing operation.

For example, in some embodiments, source electronic device 202 encryptsthe activity advertisement message (see FIG. 3, step 310) and/or theextended activity data (see FIG. 6, step 608) using an encryption keyacquired during the cloud pairing operation that source electronicdevice 202 performs with companion electronic device 204. In someembodiments, companion electronic device 204 encrypts the request forextended activity data (see FIG. 5, step 512) and/or the notificationthat the activity was transferred (see FIG. 5, step 518) using the samesecurity information, different security information acquired during thecloud pairing operation that companion electronic device 204 performswith source electronic device 202, and/or information derived fromsecurity information acquired during the cloud pairing operation.

Determining the Second Application Using an Activity Identifier

As described earlier, in some embodiments, an electronic devicedetermines whether a second application that is associated with a firstapplication is available in the electronic device (to facilitate apossible transfer of an activity to the electronic device). FIG. 7presents a flowchart illustrating a process for determining whether asecond application is available at companion electronic device 204 inaccordance with some embodiments. The operations shown in FIG. 7 can beperformed during the process shown in FIG. 5, e.g., at step 504. Notethat the operations shown in FIG. 7 are presented as a general exampleof operations performed by some embodiments. The operations performed bysome embodiments include different operations and/or operations that areperformed in a different order. Additionally, although certainmechanisms are used in describing the operations (e.g., companionelectronic device 204, etc.), in some embodiments, other mechanismsperform the operations. For example, one or both of source electronicdevice 202 and second source electronic device 206 may perform similaroperations to determine for themselves whether a second application isavailable.

The process shown in FIG. 7 begins when companion electronic device 204determines whether a flag in the activity advertisement message isasserted (step 700). As described earlier, in some embodiments, sourceelectronic device 202 asserts a flag in the activity advertisementmessage to indicate that the activity identifier is/comprises arepresentation of a domain name for the advertised activity. In some ofthese embodiments, companion electronic device 204 determines that theactivity advertisement message comprises a representation of a domainname by determining that the flag is asserted. Flags are described inmore detail later in this description, e.g., with reference to FIGS. 11and 13.

If a flag in the activity advertisement message is asserted (step 700,yes), companion electronic device 204 processes the flag (step 702). Theprocessing of the flag which takes place at step 702 is described laterwith reference to FIG. 8. Some embodiments repeat step 702 (i.e., theprocessing described with reference to FIG. 8) for each asserted flag inthe activity advertisement message, e,g., repeat the processing for eachasserted flag when the activity advertisement message comprises two ormore asserted flags.

If the activity advertisement message does not comprise a flag that isasserted (step 700, no), companion electronic device 204 compares theactivity identifier from the activity advertisement message to activityidentifiers for activities that are available at companion electronicdevice 204 (step 704). For example, companion electronic device 204 canlook up the activity identifier from the activity advertisement messagein activity identifiers in the available-activity table at companionelectronic device 204 (or other structure where companion electronicdevice 204 stores available activity information, as described earlierwith reference to FIG. 4).

If the lookup for the activity identifier finds a match in an entry inthe available-activity table (step 706, yes), companion electronicdevice 204 determines that the second application is the applicationwhose activity identifier is stored in that entry (step 708).

If the lookup for the activity identifier does not find a match in theavailable activity information (step 706, no), companion electronicdevice 204 determines that an application associated with the firstapplication is not available at companion electronic device 204 (step710).

Determining the Second Application Using a Flag

As described earlier, some embodiments assert a flag in the activityadvertisement message. FIG. 8 presents a flowchart illustrating aprocess for determining the second application using a flag inaccordance with some embodiments. More specifically, FIG. 8 presents aflowchart illustrating a process that companion electronic device 204performs at step 702 of FIG. 7. Note that the operations shown in FIG. 8are presented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., companion electronic device 204, etc.), in someembodiments, other mechanisms perform the operations. For example, oneor both of source electronic device 202 and second source electronicdevice 206 may perform similar operations for themselves.

The process shown in FIG. 8 begins when companion electronic device 204determines an application corresponding to the flag (step 800). In someembodiments, companion electronic device 204 uses the position of theasserted flag and/or the value of the flag to determine the applicationcorresponding to the flag. For example, when the activity advertisementmessage includes more than one flag that can be asserted, each of theflags can be used to identify a different application that can be usedto continue the activity. In some embodiments, the flag is a multi-bitfield and different values of the multi-bit field identify a differentapplication. In some embodiments, companion electronic device 204 storesa mapping that identifies the application that the position/value of theflags corresponds to.

Next, companion electronic device 204 determines whether the applicationcorresponding to the flag is available at companion electronic device204 (step 802). For example, companion electronic device 204 can checkwhether the application corresponding to the flag is installed atcompanion electronic device 204. In some embodiments, step 802 is notperformed/is skipped, so that the process shown in FIG. 8 continues fromstep 800 to step 804. For example, step 802 is not perforated inembodiments that use flags to identify only pre-installed applicationsthat are known to be available at companion electronic device 204 andcannot be uninstalled by a user.

If the application corresponding to the flag is available (step 802,yes), companion electronic device 204 determines that the secondapplication is the application corresponding to the flag (step 804). Theprocess then ends, which can include continuing to step 506 in FIG. 5.

If the application corresponding to the flag is not available atcompanion electronic device 204 (step 802, no), the process ends. Atthis point, companion electronic device 204 can determine that thesecond application is not available (e.g., as in FIG. 5, step 504, no),or can continue to step 704 in FIG. 7 to determine whether the secondapplication is available by using the activity identifier from theactivity advertisement message.

In some embodiments, the process shown in FIG. 8 allows an applicationdifferent than the first application to continue the activity atcompanion electronic device 204. For example, consider the case wherethe first application is a web browser and the activity performed in thefirst application includes browsing a social-media website. In thisexample, the second application can be a social-media app that accessesresources (e.g., social media user pages, etc.) accessed in the firstapplication/web browser (i.e., the second application is an app and nota web browser). By using the flag, these embodiments can configure thesocial-media app to continue the activity that was being performed atthe social-media website, at the same point where the web browser leftoff. As another example, in some embodiments, the first application is astandalone media-streaming app that streams a movie from a website (suchas a media player app) and the second application is a web browser thancan stream the movie. By using the flag, these embodiments configure theweb browser to continue playing the movie, which can include using theextended activity data for the activity to cause the web browser tocontinue playing the movie where the media-streaming app left off.

in some embodiments, source electronic device 202 sets a second flag (ora different value for the flag) in the activity advertisement message toindicate that source electronic device 202 will subsequently provideinstructions information on how to continue the activity at companionelectronic device 204. In some embodiments, the applicationcorresponding to the flag comprises the instructions/information on howto continue the activity at companion electronic device 204. In someembodiments, the extended activity data provides theinstructions/information for continuing the activity at companionelectronic device 204.

Determining the Second Application Using a Structure Storing AdvertisedActivities

As described earlier with reference to FIG. 3, in some embodiments, theactivity identifier in the activity advertisement message identifies anentry in a structure (e.g., a table) in which the electronic device thatadvertised the activity stores activity information for the advertisedactivity. FIG. 9 presents a flowchart illustrating a process fordetermining whether the second application is available when theactivity identifier identifies an entry in such a structure inaccordance with some embodiments. More specifically, during the processshown in FIG. 9, companion electronic device 204 uses an activityidentifier that identifies an entry in an advertised-activity tablewhere source electronic device 202 stored activity information for theadvertised activity to determine whether a second application that isassociated with the first application is available at companionelectronic device 204 (examples of advertised-activity tables aredescribed in more detail below with reference to FIG. 12). Note that theoperations shown in FIG. 9 are presented as a general example ofoperations performed by some embodiments. The operations performed bysome embodiments include different operations and/or operations that areperformed in a different order. Additionally, although certainmechanisms are used in describing the operations (e.g., sourceelectronic device 202, companion electronic device 204), in someembodiments, other electronic devices and/or mechanisms perform theoperations.

The process shown in FIG. 9 begins when companion electronic device 204receives an activity identifier that identifies an entry in anadvertised-activity table where source electronic device 202 storedactivity information for the advertised activity (step 900). In someembodiments, the activity identifier includes a table identifier and anentry index, the table identifier identifying the advertised-activitytable in which source electronic device 202 stored the activityinformation for the advertised activity, and the entry index identifyingthe entry in the advertised-activity table identified by the tableidentifier in which the activity information for the advertised activityis stored. In some embodiments, the table identifier is a hash of theadvertised-activity table data.

Next, companion electronic device 204 determines whether theadvertised-activity table for the activity identifier is available atcompanion electronic device 204 (step 902). In some embodiments,companion electronic device 204 uses the table identifier from theactivity identifier to determine whether companion electronic device 204has stored a local copy of the advertised-activity table.

If the advertised-activity table for the activity identifier is notavailable at companion electronic device 204 (step 902, no), companionelectronic device 204 retrieves the advertised-activity table fromsource electronic device 202 (step 904). In some embodiments, companionelectronic device 204 requests that source electronic device 202 sendthe advertised-activity table identified by the activity identifier fromthe activity advertisement message, e.g., the advertised-activity tableidentifier by the table identifier. Companion electronic device 204 cantransmit such a request, and source electronic device 202 can respond tothe request, using communication signals 208 and/or a differentcommunication signals/a different channel.

In some embodiments, companion electronic device 204 periodicallysynchronizes its local copy/copies of advertised-activity tables withsource electronic device 202. For example, companion electronic device204 may receive a copy of an advertised-activity table from sourceelectronic device 202 using a “push” mechanism, i.e., without sending arequest for the copy of the advertised-activity table.

If the advertised-activity table for the activity identifier isavailable at companion electronic device 204 (step 902, yes), or afterreceiving the advertised-activity table from source electronic device202, companion electronic device 204 uses the activity identifier toretrieve the activity information from the advertised-activity table(step 906). For example, companion electronic device 204 can retrievethe activity information from the entry in the advertised-activity tablethat is identified by the entry index.

In some embodiments, the operations shown in FIG. 9 enable informationdescribing more than one activity to be advertised in a single activityadvertisement message. For example, consider the case where the size ofthe activity advertisement message is limited, e.g., because oflimitations of a network protocol used to broadcast the activityadvertisement message. In this case, an entry identifier, i.e., anactivity identifier that identifies an entry where activity informationis stored, can be smaller (e.g., represented using fewer bits than theactivity identifier) than an encoded representation, i.e., an activityidentifier generated from the same activity information, enabling theseembodiments to carry multiple entry identifiers in an activityadvertisement message.

As described earlier with reference to FIG. 3, the described embodimentsare not limited to using a table for storing the available activityinformation. Some embodiments use a different structure for storing theavailable activity information, such as an associative array, acontent-addressable memory, etc. In these embodiments, the activityidentifier can identify an entry in a structure in which sourceelectronic device 202 stores activity information for the advertisedactivities. For example, in these embodiments, the table identifier canidentify the structure and the entry index can identify the index in thestructure where source electronic device 202 stored the activityinformation for the advertised activity.

Also, although we describe embodiments that use one advertised-activitytable, some embodiments use more than one advertised-activity table,e.g., store activity information for advertised activities in differentadvertised-activity tables.

Determining a Most Recent Activity

As described earlier, network environment 200 can include a secondsource electronic device, which can broadcast activity advertisementmessages for activities performed at the second source electronicdevice. As was also described earlier, some embodiments include atimestamp in an activity advertisement message to indicate the time thatthe activity advertised in the activity advertisement message was lastperformed. FIG. 10 presents a flowchart illustrating a process fordetermining a most recent activity from two or more activityadvertisement messages in accordance with some embodiments. Morespecifically, during the process shown in FIG. 10, companion electronicdevice 204 uses a timestamp included with the advertisement from sourceelectronic device 202 (“activity advertisement”) and a timestampincluded an advertisement from second source electronic device 206(“second activity advertisement”) to determine the most recent of theactivities advertised in the activity advertisement and the secondactivity advertisement. Note that the operations shown in FIG. 10 arepresented as a general example of operations performed by someembodiments. The operations performed by some embodiments includedifferent operations and/or operations that are performed in a differentorder. Additionally, although certain mechanisms are used in describingthe operations (e.g., source electronic device 202, companion electronicdevice 204, second source electronic device 206), in some embodiments,other electronic devices and/or mechanisms perform the operations.

For the process shown in FIG. 10, it is assumed that companionelectronic device 204 has already received the activity advertisementfrom source electronic device 202, e.g., as shown in FIG. 5. Therefore,companion electronic device 204 has the activity advertisement,including a first timestamp included with the activity advertisement.

The process shown in FIG. 10 begins when companion electronic device 204receives the second activity advertisement (step 1000). Next, companionelectronic device 204 compares the first timestamp included with theactivity advertisement with a second timestamp included with the secondactivity advertisement (step 1002). For example, companion electronicdevice 204 can compare the timestamps to see which one is newer (i.e.,indicates a more recent time).

If the comparison indicates that the first timestamp is newer (step1004, yes), companion electronic device determines that the activityperformed in the first application, i.e., the activity advertised in theactivity advertisement, is the most recent activity (step 1006).Otherwise, if the comparison indicates that the second timestamp isnewer (step 1004, no), companion electronic device 204 determines thatthe activity performed in the second application, i.e., the activityadvertised in the second activity advertisement, is the most recentactivity (step 1008).

In some embodiments, companion electronic device 204 reduces the numberof indications that are presented to a user in a display of companionelectronic device 204 (e.g., as shown in FIG. 14) by only presenting anindication that an activity is resumable for the most recent of theadvertised activities. In some embodiments, companion electronic device204 uses timestamps to present the indications that activities areresumable in order, e.g., to present the most recent activity first,followed by other advertised activities in descending order based onrelative recentness. In these embodiments, two or more indications canbe presented side-by-side, one above the other, etc. in accordance withthe relative recentness of the corresponding activities.

In some embodiments, companion electronic device 204 uses a history ofactivities that have previously been continued to present indicationsfor activities that are resumable in order. In some embodiments,companion electronic device 204 ranks activities that have previouslybeen continued higher in order, i.e., presents an indication that anactivity that has previously been continued is resumable ahead of anindication that an activity that has not previously been continued isresumable. In some embodiments, two or more indications are presented inorder based on a number of times that each of the correspondingactivities have previously been continued.

Activity Information

As described earlier, some embodiments use activity information thatdescribes an activity performed at an electronic device. FIG. 11presents a block diagram illustrating activity information 1100,activity information 1110, and activity information 1120 in accordancewith some embodiments. Note that activity information 1100, activityinformation 1110, and activity information 1120 shown in FIG. 11 arepresented as a general example of formats of activity information usedby some embodiments. Some embodiments use a different format and/orinclude different information in activity information.

Activity information 1100 includes application identifier 1102, whichidentifies the application used to perform the activity described inactivity information 1100. For example, application identifier 1102,which includes the string com.apple.Keynote, identifies applicationKeynote, an application that can be used to edit and view presentations.Activity descriptor 1104 includes the string EditPresentation, whichidentifies the activity performed with application Keynote as editing apresentation. Timestamp 1106, which includes the string/number 103,identifies a time that the activity was last performed, for example, thelast time that a user edited the presentation in application Keynote.The timestamp can indicate a real time, e.g., the wall-clock time (or arepresentation thereof, such as a system time) when the activity waslast performed, or it can be a representation of time elapsed since theactivity was last performed after the top of the hour, or since asynchronization event. In some embodiments, the timestamp indicates areal time, e.g., the absolute/wall-clock time (or a representationthereof, such as a system time) when source electronic device 202 waslast used (e.g., last used actively by a user), or it can be arepresentation of time elapsed since source electronic device 202 waslast used try after the top of the hour, or since a synchronizationevent. In activity information 1100, flag 1108 is not asserted.

Activity information 1110 includes application identifier 1112, whichidentifies the application used to perform the activity described inactivity information 1110. For example, application identifier 1112,which includes the string com.apple.Mail, identifies application Mail,an application that can be used to compose and send e-mail messages.Activity descriptor 1114 includes the string ComposeDraft to identifythat the activity performed with application Mail includes composing amessage draft. Timestamp 1116, which includes string/number 315,identifies a time that the activity was last performed, for example, thelast time that the user used Mail to compose the draft. Flag 1118 foractivity information 1110 is not asserted.

Activity information 1120 includes application identifier 1122, whichidentifies the application used to perform the activity described inactivity information 1120. For example, application identifier 1122,which includes the string com.apple.Safari, identifies applicationSafari, a web browser. Activity descriptor 1124 includes the stringwww.evideostreamer.com, which identifies a domain name accessed with theweb browser. In this example, activity descriptor 1124 holds a domainname, so flag 1128 in activity information 1120 is asserted flag 1128 toindicate that activity description 1124 comprises a domain name.Timestamp 1126, which includes string/number 820, identifies a time thatthe web browser was last used to access the move-streaming website.

Activity information 1130 includes application identifier 1132, whichidentifies the application used to perform the activity described inactivity information 1130. For example, application identifier 1132,which includes the string com.CompanyA.MediaPlayer, identifiesapplication MediaPlayer (which in this example is developed by developerCompanyA), an application that can be used to play and record multimediacontent. Activity descriptor 1134 includes the string PlayVideo toidentify that the activity performed with application MediaPlayerincludes playing a video, i.e., video playback. Timestamp 1136, whichincludes string/number 902, identifies a time that the activity was lastperformed, for example, the last time that the user used MediaPlayer toplay the video. Flag 1138 for activity information 1130 is not asserted.

For illustrative purposes, the timestamps shown in FIG. 11 arecalculated as a delta (difference) from a synchronization event, e.g.,the top of the hour. Hence, in the examples shown in FIG. 11, theactivity described with activity information 1100 is the most recentactivity, because timestamp 1106 indicates that the least amount of timehas elapsed from the top of the hour since the activity described withactivity information 1100 was performed.

Note that, although the examples shown in FIG. 11 use strings for theapplication identifier and the activity descriptor, some embodiments mayuse different information to identify the application and/or theactivity. For example, some embodiments use a numerical identifier forthe application identifier and/or the activity descriptor. In someembodiments, the application identifier is an identifier for thecorresponding application in an online “app store.” In some embodiments,the application identifier comprises some or all of a bundle identifier,e.g., a bundle ID. Also, although the application identifier shown isseparate from the activity descriptor, some embodiments combine theapplication identifier and the activity descriptor in a singleidentifier.

In some embodiments, application/app developers provide the informationfor the activity descriptors, such as activity descriptor 1104, activitydescriptor 1114, activity descriptor 1124, and activity descriptor 1134.1n these embodiments, the developer of an application/app may determinea number of activities for the application/app and may provide relevantvalues for activity descriptors.

Advertised-Activity Table

FIG. 12 presents a block diagram illustrating an advertised-activitytable 1200 in accordance with some embodiments. As described above,advertised-activity table 1200 includes information about activitiesthat have been advertised activities for which an activity advertisementmessage has been sent by an electronic device such as source electronicdevice 202). Note that the advertised-activity table shown in FIG. 12 ispresented as a general example of advertised-activity tables used bysome embodiments. Some embodiments represent activity informationdifferently and/or include more or less information in theadvertised-activity table.

Entry 1202, which is identified by entry index 1206, stores activityinformation 1100 and activity identifier 1204. In this example, activityidentifier 1204 is generated using application identifier 1102 andactivity descriptor 1104, such as a hash of string“com.apple.Keynote::EditPresentation.”

Entry 1212, which is identified by entry index 1216, stores activityinformation 1110 and activity identifier 1214. In this example, activityidentifier 1214 is generated using application identifier 1112 andactivity descriptor 1114, such as a hash of string“com.apple.Mail::ComposeDraft.”

Entry 1222, which is identified by entry index 1226, stores activityinformation 1120 and activity identifier 1224. In this example, activityidentifier 1224 is generated using activity descriptor 1124, such as ahash of string www.evideostreamer.com.

Entry 1232, which is identified by entry index 1236, stores activityinformation 1130 and activity identifier 1234. In this example, activityidentifier 1234 is generated using application identifier 1132 andactivity descriptor 1134, such as a hash of string“com.CompanyA.MediaPlayer::PlayVideo. ”

For illustrative purposes, entries 1202-1232 store all of activityinformation 1100-1130, respectively. Note though that, in someembodiments, entries 1202-1232 store only some of activity information1100-1130, respectively. For example, some embodiments do not storetimestamps 1106-1136 in entries 1202-1232.

Available-Activity Table

In some embodiments, the above-described available-activity table isformatted similarly to advertised-activity table 1200 shown in FIG. 12.However, the entries in the available-activity table include applicationinformation for applications that are available in the correspondingelectronic device, e.g., companion electronic device 204.

Activity Advertisement Message

FIG. 13 presents a block diagram illustrating an activity advertisement1300, e.g., an activity advertisement message, in accordance with someembodiments. Note that the activity advertisement message shown in FIG.13 is presented as a general example of an activity advertisementmessage used by some embodiments. Some embodiments order fields in theactivity advertisement message differently and/or include differentinformation in the activity advertisement message.

Activity advertisement message 1300 optionally includes device ID field1302 and version ID field 1304. Device ID field 1302 includes anidentifier that identifies the device from which activity advertisementmessage 1300 was sent, e.g. identifies source electronic device 202.Version ID field 1304 includes a version identifier, such as a versionidentifier that companion electronic device 204 can use to determine howfields in activity information 1300 are formatted and/or how informationis stored in the fields.

Activity identifier field 1306 includes an activity identifier, e.g.,one or more of activity identifiers 1204-1224. Flags field 1308 includesone or more flags corresponding to the advertised activity, e.g., flag1108-1128.

Timestamp field 1310 includes a timestamp for an activity advertised inactivity identifier field 1306, e.g., one or more of timestamps1106-1126.

Resumable-Activity Indication

As described earlier, some embodiments present an indication that theactivity is resumable before requesting the extended activity data. FIG.14 presents a block diagram illustrating a resumable-activityindication, i.e., an indication that an activity is resumable, inaccordance with some embodiments. More specifically, FIG. 14 shows aresumable-activity indication displayed on display 1400 for companionelectronic device 204. Note that the resumable-activity indication shownin FIG. 14 is presented as a general example of a resumable-activityindication used by some embodiments. Some embodiments use a differentresumable-activity indication and/or present the resumable-activityindication differently.

In the illustrated embodiment, companion electronic device 204 is asmartphone that comprises a touch-screen display 1400. The embodimentshown in FIG. 14 is in a receptive state because display 1400 shows alock screen with unlock indicator 1402, which shows the phrase “slide tounlock.” Generally, a user of companion electronic device 204 performsan operation with unlock indicator 1402 to unlock companion electronicdevice 204, such as sliding a graphic for unlock indicator 1402 acrossdisplay 1400 with a finger.

Resumable-activity indication 1404 comprises a graphic, e.g., an icon,that a user can manipulate to accept (or reject) the activity transfer.In FIG. 14, resumable-activity indication 1404 comprises an iconresembling an envelope, indicating that the resumable activity includesusing a mail application. In some embodiments the user can accept theactivity transfer by clicking on/touching resumable-activity indication1404, and/or by moving resumable-activity indication 1404 along a pathon display 1400. For example, in some embodiments the user can acceptthe activity transfer by touching and dragging resumable-activityindication 1404 along or near path 1406 (shown as a dotted line).

For illustrative purposes, resumable-activity indication 1404 is shownat a lock screen for companion electronic device 204. In someembodiments, resumable-activity indication 1404 can be shown at adifferent screen/location, e.g., at an unlocked screen, at a menu bar,by using a notification window/pop-up, etc. Also, the position, size,graphic, color and/or other visual features of resumable-activityindication 1404 can vary for different embodiments, and can depend onthe type of activity that can be resumed. For example, in someembodiments companion electronic device 204 determines the graphic shownin resumable activity indication 1404 based on the applicationidentifier for the advertised activity. As another example, in someembodiments resumable-activity indication 1404 is shown at the lowerleft corner of display 1400. Some embodiments present multipleresumable-activity indicators at the same time.

Note that accepting (or rejecting) the activity transfer can includemoving resumable-activity indication 1404 along a different path thanpath 1406, e.g., to the top of the screen, along a curved path, etc. Insome embodiments, the user can accept the activity transfer by clickingon resumable-activity indication 1404, by tapping on resumable-activityindication 1404, by swiping resumable-activity indication 1404, byperforming a gesture using resumable-activity indication 1404, etc.

Automatic and Manual Activity Advertisement

In some embodiments, source electronic device 202 broadcasts activityadvertisements automatically, e.g., at predetermined time intervals, assoon as activity information is received, based on a detected locationof source electronic device 202, etc. In these embodiments, sourceelectronic device 202 can provide a setting, e.g., a system preference,that a user can use to turn the broadcasting of activity advertisementson or off.

In some embodiments, source electronic device 202 starts broadcastingactivity advertisements manually, i.e., waits for input from a user tobegin broadcasting the activity advertisements. In some of theseembodiments, source electronic device 202 starts broadcasting activityadvertisements upon detecting the user's input, and continues tobroadcast activity advertisements for a predetermined period of timeand/or until the user provides an input directing source electronicdevice 202 to stop the activity advertisements. In some embodiments, theuser input for starting and/or stopping activity advertisements includesmotion of source electronic device 202 (e.g., shaking source electronicdevice 202, moving source electronic device 202 in an arc, rockingsource electronic device 202, etc.), performing one or more gestures ona touch screen for source electronic device 202, pressing a key and/orbutton combination, etc.

In some embodiments, the activity advertisement message and/or a messagethat source electronic device 202 sends to companion electronic device204 along with (i.e., in addition to) the activity advertisement messagecauses companion electronic device 204 to start a timer. In someembodiments, companion electronic device 204 remains in the receptivestate as described above until this timer expires. Source electronicdevice 202 can provide an expiry time for the timer to companionelectronic device 204, or companion electronic device 204 can determinethe expiry time.

In some embodiments, companion electronic device 204 presents anindication that the activity is resumable until the timer expires, and,if the user accepts the indication, continues the activity at companionelectronic device 204 without the user performing one or more operations(e.g., fingerprint scan, password entry, etc.) to unlock companionelectronic device 204. More specifically, companion electronic device204 can detect that the user accepted the indication and can bypass thelock screen/unlock operation, allowing the user to start using companionelectronic device 204 without unlocking companion electronic device 204.In some embodiments, the user is allowed to bypass the lockscreen/unlock operation only before the timer expires.

Activity Continuation Framework

In some embodiments, a third-party application receives access to someor all of the activity transfer operations, e.g., operations describedearlier with reference to FIGS. 3-10, through an “activity continuation”framework that is available at electronic devices that can participatein activity transfer operations. The activity continuation framework canprovide the third-party application access to an operating systemfunction, a daemon, a process, a service, etc., that performs at leastsome of the activity transfer operations. For example, in someembodiments, the provider of an electronic device and/or operatingsystem for the electronic device provides an application programminginterface (API) through which third-party applications can make calls tofunctions that facilitate activity transfer operations. In someembodiments, the activity continuation framework enables third-partyapplications (and third-party application developers) to transfer anactivity from one electronic device to another electronic device withoutimplementing (or even having knowledge of) the low-level details ofactivity continuation.

For example, in some embodiments, to enable the third-party applicationto participate in activity transfer operations, the third-partyapplication developer provides activity descriptors for activities thatthe third-party application can perform and a method for the third-partyapplication to be configured to perform an activity. In some of theseembodiments, at an electronic device such as source electronic device202, the third-party application makes a call to a function provided bythe activity continuation framework to provide an activity descriptor(and possibly extended activity data) for an activity performed in thethird-party application. At an electronic device such as companionelectronic 204, to configure the third-party application to perform theactivity, the activity continuation framework can pass the extendedactivity data to the third-party application (e.g., through a commandline switch or parameter, by using an object, etc.). Hence, the activitycontinuation framework can facilitate activity continuation forthird-party applications with minimal effort and expense for thethird-party application developer.

Messages Exchanged Between Electronic Devices

FIG. 15 presents a swim lane diagram illustrating messages exchangedbetween electronic devices in accordance with some embodiments. As canbe seen in FIG. 15, the messages are exchanged between source electronicdevice 202 and companion electronic device 204 over a period of time,with activity advertisement 1500 occurring first in time and the lowermessages occurring subsequently in time. Although FIG. 15 is shown withmessages exchanged in a particular order, in some embodiments, othermessages are exchanged and/or messages are exchanged in a differentorder. Generally, electronic devices in the described embodimentsexchange sufficient messages to enable the operations herein described.

The messages in FIG. 15 are associated with two operations performed bysource electronic device 202 and/or companion electronic device 204. Thefirst operation, which includes advertisement 1500, is an activityadvertisement operation such as is shown in FIG. 3. During the activityadvertisement operation, source electronic device 202 broadcasts atleast one activity advertisement 1500.

The second operation, which includes request for extended activity data1502, extended activity data 1504, and notification of activity transfer1506, is an activity transfer operation such as shown in FIGS. 5-6.During the activity transfer operation, companion electronic device 204responds to activity advertisement 1500 with request for extendedactivity data 1502. Upon receiving the request for extended activitydata 1502, source electronic device 202 responds by sending extendedactivity data 1504. In some embodiments, after companion electronicdevice 204 uses the extended activity data to commence performing theactivity at the second application, companion electronic device 204sends notification of activity transfer 1506 to let source electronicdevice 202 know that the activity was transferred.

The foregoing descriptions of embodiments have been presented only forpurposes of illustration and description. They are not intended to beexhaustive or to limit the embodiments to the forms disclosed.Accordingly, many modifications and variations will be apparent topractitioners skilled in the art. Additionally, the above disclosure isnot intended to limit the embodiments. The scope of the embodiments isdefined by the appended claims.

1. (canceled)
 2. A method, comprising: in a source electronic device,performing operations for: receiving, from a companion electronicdevice, a request for extended activity data corresponding to anactivity performed in a first application at the source electronicdevice; sending a notification to the first application to perform anupdate in response to receiving the request for the extended activitydata; and transmitting, to the companion electronic device, the extendedactivity data in response to receiving the request for the extendedactivity data, wherein the extended activity data is acquired afterupdating the first application.
 3. The method as recited in claim 2,wherein the extended activity data is updated with the firstapplication.
 4. The method as recited in claim 2, further comprising:sending, by the source electronic device, an activity message to thecompanion electronic device prior to receiving the request for theextended activity data, the activity message comprising an indication ofthe activity performed in the first application at the source electronicdevice, wherein the activity information comprises an identifier thatidentifies the first application and an activity descriptor thatidentifies the activity performed in the first application.
 5. Themethod as recited in claim 4, further comprising: receiving, at thesource electronic device, activity information from the firstapplication describing the activity performed in the first application;determining an identifier that identifies the first application;determining an activity descriptor that identifies the activityperformed in the first application; and determining an activityidentifier corresponding to the activity information based on theidentifier and the activity descriptor, wherein the activity messagecomprises the activity identifier.
 6. The method as recited in claim 5,further comprising: generating, at the source electronic device, anencoded representation of the activity identifier by applying a functionto the activity information that creates the encoded representation thatis smaller in size than the activity information and configured torepresent both the first application and the activity performed in thefirst application, wherein the activity message is broadcast by thesource electronic device, the activity message further comprising theencoded representation and an indication that information will beprovided on how to perform the activity for a second application on thecompanion device, wherein the second application is different from thefirst application.
 7. The method as recited in claim 2, furthercomprising: receiving, at the source electronic device, a notificationthat the activity is transferred to the companion electronic device inresponse to transmitting the extended activity data.
 8. The method asrecited in claim 2, further comprising: notifying, by the sourceelectronic device, the first application that the activity istransferred to the companion electronic device.
 9. A source electronicdevice, comprising: a processing subsystem; and a networking subsystem,wherein the processing subsystem and the networking subsystem areconfigured to perform operations for: receiving, from a companionelectronic device, a request for extended activity data corresponding toan activity performed in a first application at the source electronicdevice; sending a notification to the first application to perform anupdate in response to receiving the request for the extended activitydata; and transmitting, to the companion electronic device, the extendedactivity data in response to receiving the request for the extendedactivity data, wherein the extended activity data is acquired afterupdating the first application.
 10. The source electronic device asrecited in claim 9, wherein the extended activity data is updated withthe first application.
 11. The source electronic device as recited inclaim 9, wherein the processing subsystem and the networking subsystemare further configured to perform operations for: sending, by the sourceelectronic device, an activity message to the companion electronicdevice prior to receiving the request for the extended activity data,the activity message comprising an indication of the activity performedin the first application at the source electronic device, wherein theactivity information comprises an identifier that identifies the firstapplication and an activity descriptor that identifies the activityperformed in the first application.
 12. The source electronic device asrecited in claim 11, wherein the processing subsystem and the networkingsubsystem are further configured to perform operations for: receiving,at the source electronic device, activity information from the firstapplication describing the activity performed in the first application;determining an identifier that identifies the first application;determining an activity descriptor that identifies the activityperformed in the first application; and determining an activityidentifier corresponding to the activity information based on theidentifier and the activity descriptor, wherein the activity messagecomprises the activity identifier.
 13. The source electronic device asrecited in claim 12, wherein the processing subsystem and the networkingsubsystem are further configured to perform operations for: generating,at the source electronic device, an encoded representation of theactivity identifier by applying a function to the activity informationthat creates the encoded representation that is smaller in size than theactivity information and configured to represent both the firstapplication and the activity performed in the first application, whereinthe activity message is broadcast by the source electronic device, theactivity message further comprising the encoded representation and anindication that information will be provided on how to perform theactivity for a second application on the companion device, wherein thesecond application is different from the first application.
 14. Thesource electronic device as recited in claim 9, wherein the processingsubsystem and the networking subsystem are further configured to performoperations for: receiving, at the source electronic device, anotification that the activity is transferred to the companionelectronic device in response to transmitting the extended activitydata.
 15. The source electronic device as recited in claim 9, whereinthe processing subsystem and the networking subsystem are furtherconfigured to perform operations for: notifying, by the sourceelectronic device, the first application that the activity istransferred to the companion electronic device.
 16. A non-transitorycomputer readable storage medium storing instructions that, whenexecuted by a processing subsystem in a source electronic device, causethe source electronic device to perform a method comprising: receiving,from a companion electronic device, a request for extended activity datacorresponding to an activity performed in a first application at thesource electronic device; sending a notification to the firstapplication to perform an update in response to receiving the requestfor the extended activity data; and transmitting, to the companionelectronic device, the extended activity data in response to receivingthe request for the extended activity data, wherein the extendedactivity data is acquired after updating the first application.
 17. Thenon-transitory computer readable storage medium as recited in claim 16,wherein the extended activity data is updated with the firstapplication.
 18. The non-transitory computer readable storage medium asrecited in claim 16, wherein the method further comprises: sending, bythe source electronic device, an activity message to the companionelectronic device prior to receiving the request for the extendedactivity data, the activity message comprising an indication of theactivity performed in the first application at the source electronicdevice, wherein the activity information comprises an identifier thatidentifies the first application and an activity descriptor thatidentifies the activity performed in the first application.
 19. Thenon-transitory computer readable storage medium as recited in claim 18,wherein the method further comprises: receiving, at the sourceelectronic device, activity information from the first applicationdescribing the activity performed in the first application; determiningan identifier that identifies the first application; determining anactivity descriptor that identifies the activity performed in the firstapplication; and determining an activity identifier corresponding to theactivity information based on the identifier and the activitydescriptor, wherein the activity message comprises the activityidentifier.
 20. The non-transitory computer readable storage medium asrecited in claim 19, wherein the method further comprises: generating,at the source electronic device, an encoded representation of theactivity identifier by applying a function to the activity informationthat creates the encoded representation that is smaller in size than theactivity information and configured to represent both the firstapplication and the activity performed in the first application, whereinthe activity message is broadcast by the source electronic device, theactivity message further comprising the encoded representation and anindication that information will be provided on how to perform theactivity for a second application on the companion device, wherein thesecond application is different from the first application.
 21. Thenon-transitory computer readable storage medium as recited in claim 16,wherein the method further comprises: receiving, at the sourceelectronic device, a notification that the activity is transferred tothe companion electronic device in response to transmitting the extendedactivity data.